Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1247

reference: 770-tree-1
name: 1247
tree-preservation-order: undefined
770-tpo-1
uprn
address-text
point: POINT (-1.042164 50.866770)
geometry: MULTIPOLYGON (((-1.042107 50.866764,-1.042109 50.866775,-1.042117 50.866785,-1.042130 50.866793,-1.042146 50.866799,-1.042163 50.866801,-1.042181 50.866799,-1.042197 50.866794,-1.042209 50.866786,-1.042218 50.866776,-1.042221 50.866765,-1.042218 50.866754,-1.042210 50.866744,-1.042198 50.866736,-1.042182 50.866731,-1.042165 50.866729,-1.042147 50.866730,-1.042131 50.866735,-1.042118 50.866743,-1.042110 50.866753,-1.042107 50.866764)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL